Sync all fail2ban config files with upstream (2025)#37
Merged
nemchik merged 5 commits intolinuxserver:masterfrom Sep 21, 2025
Merged
Sync all fail2ban config files with upstream (2025)#37nemchik merged 5 commits intolinuxserver:masterfrom
nemchik merged 5 commits intolinuxserver:masterfrom
Conversation
Contributor
Author
|
@nemchik please review. |
nemchik
approved these changes
Sep 21, 2025
Member
nemchik
left a comment
There was a problem hiding this comment.
I did a full review of all of this as much as I could. All of the changes are coming from upstream, so I believe this should be safe to merge.
Member
|
Thanks for this! These changes should be included in the next release of our fail2ban image. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR refreshes the bundled Fail2Ban configuration files in
action.d,filter.d,jail.dfrom upstream Fail2Ban (in sync with the latest commit: fail2ban/fail2ban@26b9186).There’s an open issue #35 “Why are the fail2ban configs so outdated?” — this PR addresses that concern by syncing all configs.
closes #35